Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upper version constraints against ef core 3 #445

Merged
merged 1 commit into from
Nov 10, 2019
Merged

upper version constraints against ef core 3 #445

merged 1 commit into from
Nov 10, 2019

Conversation

danielgerlag
Copy link
Owner

  • EF Core 3.0 introduces breaking changes
  • EF Core 3.0 targets .net standard 2.1 which will not be supported by .Net Framework
  • This PR places an upper limit on the EF core version of the host application, as this incompatibility was creating confusion that workflow core is not compatible with .net core 3.0, which is false

@terry-delph
Copy link

HI @danielgerlag

I think the MySQL persistence provider may also need this same constraint.

It depends on Pomelo.EntityFrameworkCore.MySql.

If we were to upgrade to Pomelo.EntityFrameworkCore.MySql 3.0.0-rc3.final

Dependency chain of Pomelo is:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants